File system for rolling back data on tape

ABSTRACT

Rolling back data on tape in a file system is provided. A management tape is prepared. The management tape has only index files recorded thereon. The index files contain information about start positions and lengths of corresponding data files recorded on normal tapes. The index files further contain identification information for the normal tapes. A first index file of the management tape is read. The first index file is related to a data file to be rolled back. The first index file is read out from the management tape mounted on a first tape drive. The data file to be rolled back is read out of a first normal tape. The first normal tape is identified based on information in the first index file. The first normal tape is mounted on a second tape drive.

TECHNICAL FIELD

The present invention relates to a file system including a tape drive,and more specifically, rolling back data on tape in the file system.

BACKGROUND

As a mechanism for accessing data in a tape drive as a file in a filesystem, for example, LTFS (Linear Tape File System) has been put topractical use. LTFS implements a file system by associating files withmeta information such as indices, which indicate where data areas makingup the files are located on tape.

Due to the nature of tape, LTFS is designed to add edited data, duringediting of a file, to the end of data written in the past withoutoverwriting the past data. This provides the advantage of being able toread data out of a file written in the past. In LTFS, the act of readingpast data is referred to as rollback.

A Linear Tape-Open (LTO) Ultrium tape drive available for use by LTFSdivides a tape into an index partition mainly used to write indices, anda data partition mainly used to write data. In the data partition, afteredited data is added, an index of the data is also added to the end ofthe edited data. The added index (i.e., the latest index) also includesmeta information about one-generation old data and data of earliergenerations (i.e., data edited one generation ago and earlier). Also,each index contains information (i.e., a pointer) which identifies alocation of a one-generation old index.

Rollback makes it possible to read meta information about data in a filewritten in the past (i.e., a few generations earlier) based on thelatest index on the data partition, identifying the location and thelike of data to be read out, and then reading out the data. However, ifa file of data of a past generation has already been deleted (logically)in the file system, since the index of data edited after the deletiondoes not contain meta information about the deleted data, the locationand the like of the deleted data cannot be identified directly from thelatest index created after the deletion.

In that case, information (a pointer) which identifies the location ofthe one-generation old index is read out of the latest index, andinformation (a pointer) which identifies the location of thetwo-generation old index is read out of the one-generation old index,and so on. Read operations are thus repeated by going back to previousindices to identify the location and the like of the deleted data fromthe index recorded before the deletion, and thereby the file of thedeleted data is read.

SUMMARY

According to one embodiment of the present invention, a method forrolling back data on tape in a file system is provided. The methodincludes: preparing a management tape with only index files recordedthereon, the index files containing information about start positionsand lengths of corresponding data files recorded on normal tapes, andthe index files further containing identification information for thenormal tapes; reading a first index file of the management tape, whereinthe first index file is related to a data file to be rolled back,wherein the first index file is read out from the management tapemounted on a first tape drive; and reading the data file to be rolledback out of a first normal tape, wherein the first normal tape isidentified based on information in the first index file, and wherein thefirst normal tape is mounted on a second tape drive.

According to another embodiment of the present invention, a file systemwhich allows data on tape to be rolled back using a management tape isprovided. The file system includes: a host; a first tape drive adaptedto mount normal tapes with data files recorded thereon; and a secondtape drive adapted to mount a management tape with only index filesrecorded thereon, the index files containing information about startpositions and lengths of corresponding data files recorded on the normaltapes and the index files further containing identification informationabout the normal tapes, wherein the host reads the index file related toa data file to be rolled back out, wherein the index file is read backout of the management tape mounted on the second tape drive, and thehost reads the data file to be rolled back out of the normal tapeidentified based on information in the index file, the normal tape beingmounted on the first tape drive.

According to another embodiment of the present invention, a computerprogram product for rolling back data on tape in a file system isprovided. The program is stored on non-transitory computer readablestorage media and controls a computer to perform a method, the methodincluding: preparing a management tape with only index files recordedthereon, the index files containing information about start positionsand lengths of corresponding data files recorded on normal tapes, andthe index files further containing identification information for thenormal tapes; reading a first index file of the management tape, whereinthe first index file is related to a data file to be rolled back,wherein the first index file is read out from the management tapemounted on a first tape drive; and reading the data file to be rolledback out of a first normal tape, wherein the first normal tape isidentified based on information in the first index file, and wherein thefirst normal tape is mounted on a second tape drive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing a configuration example of a file systemaccording to an embodiment of the present invention;

FIG. 2 is a diagram showing a configuration example of a host in thefile system according to an embodiment of the present invention;

FIG. 3 is a diagram showing a configuration example of a tape drive inthe file system according to an embodiment of the present invention;

FIG. 4 is a diagram showing rollback according to a conventional method;

FIG. 5 is a diagram showing a flow of a method according to anembodiment of the present invention;

FIG. 6 is a diagram showing a configuration example of a management tapeaccording to an embodiment of the present invention;

FIG. 7 is a diagram showing a configuration example of a management tapeaccording to an embodiment of the present invention;

FIG. 8 is a diagram showing effects of a method according to anembodiment of the present invention; and

FIG. 9 is a diagram showing effects of a method according to anembodiment of the present invention.

DETAILED DESCRIPTION

A first aspect of the present invention provides a method for rollingback data on tape in a file system. The method comprises the steps of:(a) preparing a management tape with only index files recorded thereon,the index files containing information about start positions and lengthsof respective data files recorded on normal tapes and identificationinformation about the normal tapes; (b) reading the index file relatedto a data file to be rolled back out of the management tape mounted on atape drive; and (c) reading the data file to be rolled back out of thenormal tape identified based on information in the read index file andmounted on the tape drive.

According to the first aspect of the present invention, since locationinformation and the like about the data file to be rolled back is readout of the management tape on which only index files have been recorded,the read can be performed in a short time and consequently the targeteddata file can be read out quickly. Also, even when a rollback process iscanceled halfway through, since no processing request is made to thenormal tape on which the data file has been recorded, a next processingrequest can be made to the normal tape without waiting for completion ofseeks on the management tape.

A second aspect of the present invention provides a file system whichallows data on tape to be rolled back using a management tape. The filesystem comprises: (a) a host; (b) a first tape drive adapted to mountnormal tapes with data files recorded thereon; and (c) a second tapedrive adapted to mount a management tape with only index files recordedthereon, the index files containing information about start positionsand lengths of respective data files recorded on the normal tapes andidentification information about the normal tapes.

The host reads the index file related to a data file to be rolled backout of the management tape mounted on the second tape drive and readsthe data file to be rolled back out of the normal tape identified basedon information in the index file and mounted on the first tape drive.

According to the second aspect of the present invention, using thesecond tape drive different from the first tape drive on which thenormal tape is mounted, location information and the like about the datafile to be rolled back is read out of the management tape on which onlythe index files have been recorded. This allows the read to be performedin a short time and consequently the targeted data file can be read outof the first tape drive quickly. Also, even when a rollback process iscanceled halfway through on the second tape drive, since no processingrequest is made on the first tape drive to the normal tape on which thedata files have been recorded, a next processing request can be made tothe normal tape on the first tape drive without waiting for completionof seeks on the management tape on the second tape drive.

Embodiments of the present disclosure recognize that utilizing LTFS toaccess files on a tape drive may provide the advantage of being able toread data out of a file written in the past. Embodiments recognize ademand for a mechanism which, in performing rollback to read deleteddata, allows an index to be read out retrospectively in a short time andalso allows the rollback to be canceled easily. Some embodiments of thepresent invention provide a file system which can provide such amechanism as well as a method for rolling back data on tape in the filesystem.

Embodiments further recognize that there is a problem in that therollback performed to read the deleted data takes time. This is becauseeach index in the data partition is written between data items, makingit necessary to retrace indices one by one until the index of a desiredgeneration is found, and thereby involving a large number of seeks (tapeand head movements and the like).

Also, once a seek is started, the tape drive cannot accept anotherrequest until the seek has been processed. This presents another problemin that once rollback is started, processing of the rollback cannot becanceled halfway through.

Embodiments of the present invention will be described with reference tothe drawings. Note that in the following description, the embodiments ofthe present invention will be described in comparison with contents of aconventional technique as required.

FIG. 1 is a diagram showing a configuration example of a file system inwhich a method according to an embodiment of the present invention isimplemented. The file system 100 includes a tape drive 10, a host(server) 30, and PCs (terminals) 32 and 34, which are capable ofintercommunications via a network 36. Although a single tape drive 10and a single host (server) 30 are shown in FIG. 1, this is merelyintended for illustration purposes, and two or more tape drives 10 maybe included, for example, as a tape library, and two or more hosts(servers) 30 may be included as well.

The file system 100 can be, for example, LTFS. Once a tape cartridge isinserted into a tape drive, LTFS allows direct access to any file savedin the tape cartridge as with an HDD and a USB memory or other removablerecording media including a CD-R. To build a file system on a tapedrive, an LTO Ultrium (such as LTO-5) tape drive can be used, forexample. With the LTO Ultrium tape drive, it is necessary that the tapeused has partitions. The partitions will be described later.

FIG. 2 is a diagram showing a configuration example of the host (server)30 shown in FIG. 1. The host (server) 30 includes a central processingunit (CPU) 301, a storage device 302, and various interfaces 304interconnected via a bus 303. The term “various interfaces 304” is usedas the general term which includes an input interface, an outputinterface, an external storage interface, and an external communicationsinterface. The interfaces are connected with appropriate one or more ofan input/output device 305, such as a keyboard, mouse, andcommunications adapter; a display device 306, such as a CRT and LCD; andan external storage device 307, such as a USB-connected semiconductormemory and HDD. The storage device 302 can include semiconductormemories such as a RAM and ROM as well as an HDD and the like. Afunction (a method) of an embodiment of the present invention isimplemented when the host (server) 30 calls and executes predeterminedsoftware stored, for example, in the storage device 302 or 307.

FIG. 3 is a diagram showing a configuration example of a tape driveavailable for use in an embodiment of the present invention. The tapedrive 10 includes a host interface (hereinafter referred to as the “hostI/F”) 11, a buffer 12, a channel 13, a head 14, and a motor 15 as wellas a controller 16, a head position control system 17, and a motordriver 18. Furthermore, a tape cartridge 20, which can be inserted andloaded in the tape drive 10, is illustrated here as well. The tapecartridge 20 contains a tape 23 wound on reels 21 and 22. Along withrotation of the reels 21 and 22, the tape 23 moves in a longitudinaldirection from the reel 21 to the reel 22 or from the reel 22 to thereel 21. Note that although a magnetic tape is illustrated as the tape23 by way of example, a tape medium other than magnetic tape may be usedalternatively.

The tape cartridge 20 also contains a cartridge memory (CM) 24. The CM24 records, for example, information as to how data has been written onthe tape 23. Then, fast data access is enabled by checking, for example,indices of data written into the tape 23 and a usage situation of thetape 23, in a contactless manner using, for example, an RF interface.Note that an interface, such as the RF interface, used to access the CM24 is shown in FIG. 2 as a cartridge memory interface (hereinafterreferred to as the “CM I/F”) 19.

Host I/F 11 communicates with the host (server) 30, another PC 32, orthe like. For example, from an OS of the host 30, the host I/F 11receives a command to write data into the tape 23, a command to move thetape 23 to a desired position, and a command to read data out of thetape 23. In the example of LTFS described above, data in the tape drivecan be referred to directly from a desktop OS or the like and a file canbe opened by double-clicking or copied by dragging and dropping, similarto handling a file on the HDD.

The buffer 12 is a memory configured to temporarily store data to bewritten into the tape 23 or data read out of the tape 23. For example,the buffer 12 is constructed from a DRAM. Also, the buffer 12 is made upof multiple buffer segments, each of which stores a data set. A data setis a unit of data in which the data is read or written with respect tothe tape 23.

The channel 13 is a communications path used to send the data to bewritten into the tape 23 to the head 14 and receive the data read out ofthe tape 23 from the head 14. As the tape 23 moves in the longitudinaldirection, the head 14 writes information into the tape 23 or readsinformation out of the tape 23. The motor 15 turns the reels 21 and 22.Note that although the motor 15 is represented by one rectangle in FIG.3, preferably a motor 15 is provided for each of the reels 21 and 22 fora total of two motors.

On the other hand, the controller 16 controls the entire tape drive 10.For example, based on a command accepted by the host I/F 11, thecontroller 16 controls data writes and reads into/from the tape 23.Also, the controller 16 controls the head position control system 17 andmotor driver 18. The head position control system 17 is a systemdesigned to track a desired lap. Here, the lap is a group of multipletracks on the tape 23. When it becomes necessary to switch the lap, italso becomes necessary to electrically switch the head 14, and suchswitching is controlled by the head position control system 17.

The motor driver 18 drives the motor 15. Note that when two motors 15are used as described above, two motor drivers 18 are provided as well.The CM I/F 19 is implemented, for example, by an RF reader-writer, andis designed to write and read information into/from the CM 24.

Now, configurations of a partition and index in LTFS in which thepresent invention is embodied will be described. LTFS uses a logicalblock on tape called a partition which has come to be supported by LTO-5and subsequent generations of LTO. LTFS uses two types of partitions: anindex partition and a data partition. The data partition is made up ofdata itself which makes up a file, and index information written whenpredetermined conditions are met after completion of a file write. Theindex partition stores the latest index information, which is read whena cartridge is loaded, and makes it possible to determine where on amedium a file exists.

FIG. 4 shows a configuration example of a conventionally available indexpartition and data partition. FIG. 4 also shows a rollback-based indexreading procedure according to a conventional method. In the example ofFIG. 4, the latest index (gen#=3) in the index partition is read outfirst, a location and the like of the latest index (gen#=3) in the datapartition are acquired, and then the latest index (gen#=3) is read out(arrow 1). A location and the like of a one-generation old index(gen#=2) are acquired from the index (gen#=3), and then the index(gen#=2) is read out (arrow 2). Similarly, a location and the like of aone-generation old index (gen#=1) are acquired from the index (gen#=2),and then the index (gen#=1) is read out (arrow 2).

The above flow makes it possible to acquire information about a locationand the like of a targeted data file of gen#=1 by rollback and to readthe data file. In this case, as already described above, each index inthe data partition is written between data items, making it necessary toretrace indices one by one as described above until the index of adesired generation is found, and thereby involving a large number ofseeks (tape and head movements and the like). Embodiments of the presentinvention provide a method, described below, that makes it possible toread an index of a desired generation in a short time by avoiding such alarge number of seeks.

FIG. 5 is a diagram showing a flow of a method according to anembodiment of the present invention. The flow shown in FIG. 5 is a basicflow of the method. The flow in FIG. 5 can be implemented using, forexample, the configuration of the file system shown in FIGS. 1 to 3.More specifically, the method provided by embodiments of the presentinvention is implemented when the host (server) 30 in FIG. 1 calls andexecutes predetermined software stored in the storage device 302 or 307.

In step S1, a management tape is prepared. The management tape means atape on which only index files are recorded, the index files containinginformation about start positions and lengths of respective data filesrecorded on normal tapes and identification information (Id) about thenormal tapes. In some embodiments of the present invention, themanagement tape with only the index files recorded thereon is used inaddition to the normal tapes. The management tape will be furtherdescribed in detail later.

In step S2, the index file containing meta information (location and thelike) about a data file to be rolled back is read out of the managementtape mounted on the tape drive. The tape drive used to mount themanagement tape may be the same as or different (i.e., a second tapedrive) from a tape drive (i.e., the first tape drive) on which thenormal tape (i.e., the user tape) is mounted. In so doing, a tape drivededicated to the management tape may be provided so that the index filecan be read promptly in response to a request from the host. Adescription of how the index file is read out of the management tapewill be given later together with details of the management tape.

In step S3, after the normal tape identified based on information in theindex file read out of the management tape is mounted on the tape drive(i.e., the first tape drive), the data file to be rolled back is readout of the normal tape. The reading operation is performed in a mannersimilar to when the data file is usually read out of the normal tape.

Example embodiments of the management tape will be described withreference to FIGS. 6 and 7. FIGS. 6 and 7 show conditions in whichmultiple index files have already been recorded on a tape.

In the example of FIG. 6, the management tape is divided into multiplepartitions 0 to X. The partitions 0 to X are assigned to normal tapes Ato X, respectively. For example, partition 0 is assigned to tape A,partition 2 is assigned to tape C, and so on.

The index files of each tape are added one after another to acorresponding one of the partitions. For example, each time an indexfile of tape B is created (updated), the index file, such as B-1, B-2,B-3, and so on, is added to partition 1. The addition is made with apredetermined timing, for example, being timed with a tapesynchronization or a tape unmount process.

In the example of FIG. 6, it is necessary to maintain informationregarding which tape corresponds to which partition, which can be doneby saving a correspondence table externally or creating a partition foruse in saving a correspondence table on the tape. In this example, sincethe index files of each tape are written consecutively, all the indexfiles can be read sequentially. In so doing, unlike the conventionalmethod (FIG. 4), the indices are read out in sequence in thechronological order of generations as indicated by arrow M1 in FIG. 6.

With the conventional method (FIG. 4), each index file is writtenbetween items of user data and consequently, locations of indices on thetape are unknown, making it necessary to derive the index of an oldgeneration from the index of a new generation. However, in the exampleof FIG. 6, since only the index files are written on the tape, making itunnecessary to find out index locations, there is no problem in readingout indices in the chronological order of generations. In this example,the tape is divided into multiple partitions at the expense of capacity.This is suitable when there are a small number of tapes or whensynchronization occurs frequently and a large number of index files arewritten, resulting in high costs of a seek process.

In the example of FIG. 7, the management tape includes a data partition(Data) and an index partition (Index) as with normal LTO Ultrium tapes.The index file of each tape is written into the data partition (Data) asone item of data. In FIG. 7, the first index file of tape A, secondindex file of tape A, first index file of tape B, and so on are added tothe data partition (Data) as A-1, A-2, B-1, and so on, respectively. Inso doing, each index in the data partition (Data) contains a file namewhich can identify the tape name (Id), generation, and the like.

Then, an index which represents a pointer (location information) to thedata (index file) added to the data partition (Data) is written into theindex partition (Index). Consequently, since the location of a desiredindex to be read during rollback can be identified by reading the indexin the index partition (Index), it is possible to move directly to theindex of a desired generation as indicated by arrow M2 in FIG. 7 withoutthe need to read the indices in sequence beginning with the first orlast index.

In the example of FIG. 7, the index files of all the tapes are writteninto one data partition (Data), allowing the capacity of the tape to beused effectively. Consequently, this method is effective when there area large number of tapes, making it difficult to divide the managementtape into as many partitions as there are tapes as shown in FIG. 6. Onthe other hand, when one wants to read all the indices of each tape, itis not possible to read the indices sequentially. However, the indexfile is normally small relative to user data, making a distance betweenthe index files on the tape shorter than on the normal tape in manycases, and consequently it is expected that a seek time taken to read anindex file is also shorter than in a process with a normal tape.

Effects of the method according to embodiments of the present inventionwill be described with reference to FIGS. 8 and 9. Specifically, theprocessing time required for rollback will be compared betweenembodiments of the present invention and the conventional method. FIGS.8 and 9 show simulation results (described later) of the processingtime. The abscissa represents the generation of indices while theordinate represents the processing time required for rollback. Thelarger the abscissa is, the newer the generation of the index is. Inother words, the smaller the abscissa is, the older the generation is.

The time required to reach index X (0<=X<G) will be calculated for atape which has G indices (index 0 to index G-1) in total. However, thiscalculation is a rough estimate intended to find a rough figure, and itis necessary to take acceleration or deceleration of the tape intoconsideration to find a precise figure. On an LTO-5 tape drive, taperunning speed during a seek is 10 m/sec while running speed during aread is 8 m/sec. Also, longitudinal length of the LTO-5 tape isapproximately 800 m.

In order to go back one generation, the conventional method requires thefollowing three processes to be performed:

1. Index file seek,2. Backhitch (rewind) for starting a read action, and3. Data read.

If it is assumed that a seek distance is ⅓ the length of the tape onaverage, the seek time is 800/ 3/10 seconds. Empirically, backhitch timeis set to 5 seconds. Reading of data depends on the index file size, butin many cases, data is sized to fit well within one data set (DS), whichis a unit used in reading and writing data in LTO format, and thusdata-reading time can be set to the time required to read one DS. Thelength of one DS corresponds to approximately 10 cm, and thus thedata-reading time is 0.1/8 seconds. Thus, the time required to rewindthe tape one generation is:

800/3/10+5+0.1/8≈31.68 seconds.

This is repeated (G-X) times, and thus a total processing time T1required for rollback is

T1=(G−X)*31.68 seconds.

In example 1 of the method according to an embodiment of the presentinvention (method of FIG. 6), an index file is read from the beginningof the tape. Thus, necessary actions are a seek for the beginning of thetape at the start of the process, backhitch, and reading of as many datasets as indices. Times required for these actions are calculated in amanner similar to the conventional method described above and are800/3/10, 5, and 0.1/8*X, respectively. Thus, a total processing time T2required for rollback is:

T2=800/3/10+5+0.1/8*X=31.67+0.0125X seconds.

In example 2 of the method according to an embodiment of the presentinvention (method of FIG. 7), an index is read out of the indexpartition (Index), and then going to the desired index file based on theinformation about the index, data is read out. That is, seeking,backhitching, and reading are each repeated twice. Thus, a totalprocessing time T3 required is:

T3=(800/3/10+5+0.1/8)*2≈63.36 seconds.

FIG. 8 shows rollback time plotted as processing time on the ordinate,assuming that the total number of indices G=10. The rollback time(processing time) is affected greatly by the number of seeks, and insome cases the conventional method can complete rollback in a shortertime depending on the value of G-X. However, it can be seen from FIG. 8that in most cases, the methods according to embodiments of the presentinvention can complete rollback in a shorter time both in Example 1 andExample 2. In particular, it can be seen that the older the generationis, the more quickly the methods according to embodiments of the presentinvention can perform rollback.

Normally, a rollback operation is performed in the following threesteps:

1. List information on all the indices on the tape.2. Select a desired generation to be rolled back from the listedinformation.3. Roll back to the specified generation.

The calculations described above provide a rough estimate of the timerequired in step 3, although the listing time in step 1 needs to beadded, as described below.

With the conventional method and example 1 of the method according to anembodiment of the present invention (method of FIG. 6), listing is anoperation similar to the operation of rolling back all generations, andthe required times are G*31.68 seconds and 31.67+0.0125X seconds,respectively. In example 2 of the method according to an embodiment ofthe present invention (method of FIG. 7), if all the information to belisted is saved in indices in the index partition (Index), all that isnecessary is to read the desired index, and the required time is thetime of seek for the index in the index partition (Index) plus the readtime, which equals 31.68 seconds. From the above calculations, the totalprocessing times of steps 1 and 3 according to the respective methodsare as follows:

Conventional method: (2G−X)*31.68 secondsExample 1 of an embodiment of the present invention: 63.36+0.025XsecondsExample 2 of an embodiment of the present invention: 95.04 seconds

This is represented graphically in FIG. 9, assuming that G=10. It can beseen that the processing time taken for the entire rollback operation isalways shorter with the methods according to embodiments of the presentinvention than with the conventional method. In particular, as in thecase of FIG. 8, it can be seen that the older the generation is, themore quickly the method according to embodiments of the presentinvention can perform rollback.

Embodiments of the present invention have been described with referenceto the drawings. However, the present invention is not limited to theembodiments. Furthermore, the present invention can be embodied in formsresulting from various improvements, modifications, or changes based onthe knowledge of those skilled in the art without departing from thespirit and scope of the invention.

To provide a method for rolling back data on tape in a file system in ashort time. A method according to the present invention includes thesteps of (a) preparing a management tape with only index files recordedthereon, the index files containing information about start positionsand lengths of respective data files recorded on normal tapes andidentification information about the normal tapes; (b) reading the indexfile related to a data file to be rolled back out of the management tapemounted on a tape drive; and (c) reading the data file to be rolled backout of the normal tape identified based on information in the read indexfile and mounted on the tape drive.

What is claimed is:
 1. A file system which allows data on tape to berolled back using a management tape, the file system comprising: a host;a first tape drive adapted to mount normal tapes with data filesrecorded thereon; and a second tape drive adapted to mount a managementtape with only index files recorded thereon, the index files containinginformation about start positions and lengths of corresponding datafiles recorded on the normal tapes, wherein the host reads the indexfile related to a data file to be rolled back out, wherein the indexfile is read back out of the management tape mounted on the second tapedrive, and the host reads the data file to be rolled back out of thenormal tape identified based on information in the index file, thenormal tape being mounted on the first tape drive.
 2. The file systemaccording to claim 1, wherein the host adds an updated index file to themanagement tape with a predetermined timing, wherein the updated indexfile is generated each time a data file recorded on the normal tapes isupdated.
 3. The file system according to claim 2, wherein: themanagement tape includes a plurality of partitions, each of theplurality of partitions corresponding; and the host adds the updatedindex file to a partition of the plurality of partitions thatcorresponds to the normal tape on which the updated data file isrecorded.
 4. The file system according to claim 2, wherein themanagement tape includes a data partition and an index partition, andwherein the host adds the updated index file to the data partition.